Facilitating payments using wearable devices

ABSTRACT

A wearable device, e.g., a smart watch, may be connected to a communication device, such as a mobile smart phone, via Bluetooth or other Near Field Communication (NFC). In particular, the wearable device may have a touch screen that may serve as an extended display and/or user input device of the communication device. For example, a user may receive payment related notifications on the wearable device. The user also may operate the wearable device to make and/or receive payments, view transaction history, view and/or accept offers from nearby merchants, view and/or check in to nearby stores and etc. Further, the wearable device also may allow the user to make payment transactions in extreme environments not suitable for the communication device, such as under water.

CROSS REFERENCE TO RELATED APPLICATION

Pursuant to 35 U.S.C. § 119(e), this application claims priority to thefiling dates of U.S. Provisional Patent Application Ser. No. 61/943,268,filed Feb. 21, 2014 and U.S. Provisional Patent Application Ser. No.61/978,695, filed Apr. 11, 2014, both of which are incorporated byreference in their entirety.

BACKGROUND

Field of the Invention

The present invention generally relates to systems and methods forfacilitating payments using wearable devices.

Related Art

In today's internet commerce, many payment transactions are made onlinevia the internet. For example, a user may use a mobile device to makepurchases and facilitate payments. Mobile devices may be connected to awearable device, such as a smart watch. When the mobile device isconnected to the peripheral device, the user may have access to thewearable device but not the mobile device itself. When the user wishesto make an online payment using the mobile device, the user has to findand bring out the mobile device, which is inconvenient to the user.Therefore, there is a need for a system or method that allows the userto facilitate payments using the wearable device.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of a networked system suitable forfacilitating payments using wearable devices according to an embodiment.

FIG. 2 is a flowchart showing a process for facilitating payments usinga wearable device according to one embodiment.

FIG. 3 is a block diagram illustrating interaction between a wearabledevice and a mobile device according to one embodiment.

FIG. 4 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1 according to one embodiment.

FIG. 5 is a diagram illustrating steps for setting up a wearable deviceaccording to one embodiment.

FIG. 6 is a user interface for setting preferences for making paymentsvia a wearable device according to one embodiment.

FIG. 7 is a user interface navigation flow chart for a wearable deviceaccording to one embodiment.

FIG. 8 illustrates various screens for various functions displayed on awearable device according to one embodiment.

FIG. 9 illustrates various notifications displayed on a wearable deviceaccording to one embodiment.

FIG. 10 is a user interface navigation flow chart for a money sendingprocess on a wearable device according to one embodiment.

FIG. 11 is a user interface navigation flow chart showing variousfunctions displayed on a wearable device according to one embodiment.

FIG. 12 illustrates various screens for various functions displayed on awearable device according to one embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

According to an embodiment, a wearable device, e.g., a smart watch, maybe connected to a communication device, such as a mobile smart phone,via Bluetooth or other Near Field Communication (NFC). In particular,the wearable device may have a touch screen that may serve as anextended display and/or user input device of the communication device.For example, a user may receive payment related notifications on thewearable device. The user also may operate the wearable device to makeand/or receive payments, view transaction history, view and/or acceptoffers from nearby merchants, view and/or check in to nearby stores,etc. Further, the wearable device also may allow the user to makepayment transactions in extreme environments may not be suitable for thecommunication device, such as under water.

In an embodiment, a system or a method may be provided to implement anapplication framework that allows a communication device to manage andimplement a plurality of different wearable devices. In particular, apayment application installed on the communication device may implementnotifications and information display on various wearable devices.Further, the payment application also may receive and implement userinstructions entered via the various wearable devices.

In an embodiment, a system or a method is provided to implement quickaccess to transaction information for high-velocity online marketsellers, such as eBay, Inc. Further, data transmission between thewearable device and the communication device may be encrypted to provideadditional security. A login process may be implemented to link thewearable device to the communication device. The user may login at leastdaily on the communication device to renew the linking session betweenthe wearable device and the communication device. The user may extendthe linking session based on notifications displayed on the wearabledevice. When the wearable device and the communication device arelinked, various functions may be available to the user via the wearabledevice. User preferences and data may be stored by the paymentapplication with the payment service provider.

In an embodiment, when the linking session remains active, the user maycheck in to various merchants or locations via the wearable device.Various functions, such as viewing offers, saving coupons and otherincentives to a wallet, storing lists and other low risk activities, maybe implemented via the wearable device. Other activities that requireadditional security may be redirected to the communication device wherethe user may implement or perform these activities that requireadditional security. In an embodiment, the user may automatically bechecked into a location or a merchant based on the user's prior consent.

In an embodiment, the payment service provider may track variouswearable devices linked to the user's payment account. As such, the usermay manage various wearable devices that interact with the user'spayment account. In another embodiment, the payment service provider maytrack payments and/or check-ins that are implemented via wearabledevices. In particular, a subset of transactions implemented viawearable devices may be tracked.

In an embodiment, the user may designate favorite places with a heartsymbol or other visual indicator. The user may automatically be checkedinto favorite places. In an embodiment, vibration alerts may be used onthe wearable device. For example, the wearable device may vibrate when alarge amount of information is sent or received, when the user ischecked into a new place, or when other beacon related events occur. Inan embodiment, the wearable device may receive voice commands. Forexample, voice commands like “order,” “send money,” or “request money”may be received at the wearable device. Other basic voice actions, suchas “check in to Jamba Juice,” or “find a coupon for coffee,” also may bereceived at the wearable device.

In another embodiment, voice control also may be used for userauthentication. For example, a confidence level may be determined basedon whether the user speaking is the same one linked to the device. Otheradvanced voice actions involving Risk and Platform tools also may beimplemented, such as “send $5 to Gerald.” In an embodiment, the wearabledevice may have camera access that may be used to scan product bar codesfrom which price comparisons may be implemented.

In an embodiment, biometrics detected at the wearable device may be usedfor user authentication. For example, accelerometer or heart ratesensors on the wearable device may collect data from the user and sharedata with the communication device. This data may be used toauthenticate the user. Other biometric data, such as voiceprint may becaptured and used for confidence scoring during authentication. One ormore fingerprint sensors also may be used to collect fingerprints of theuser for authentication.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing a process for facilitating purchases using peripheraldevices according to an embodiment. Networked system 100 may comprise orimplement a plurality of servers and/or software components that operateto perform various payment transactions or processes. Exemplary serversmay include, for example, stand-alone and enterprise-class serversoperating a server OS such as a MICROSOFT® OS, a UNIX® OS, a LINUX® OS,or other suitable server-based OS. It can be appreciated that theservers illustrated in FIG. 1 may be deployed in other ways and that theoperations performed and/or the services provided by such servers may becombined or separated for a given implementation and may be performed bya greater number or fewer number of servers. One or more servers may beoperated and/or maintained by the same or different entities.

System 100 may include a user device 110, a wearable device 102, amerchant server 140, and a payment provider server 170 in communicationover a network 160. Payment provider server 170 may be maintained by apayment service provider, such as PayPal, Inc. of San Jose, Calif. Auser 105, such as a sender or consumer, utilizes user device 110 toperform a transaction using payment provider server 170. User 105 mayutilize user device 110 to initiate a payment transaction, receive atransaction approval request, or reply to the request. User 105 mayinput instructions for making a purchase to user device 110 via wearabledevice 102. Note that transaction, as used herein, refers to anysuitable action performed using the user device, including payments,transfer of information, display of information, etc. For example, user105 may utilize user device 110 to initiate a deposit into a savingsaccount. Although only one merchant server is shown, a plurality ofmerchant servers may be utilized if the user is purchasing products orservices from multiple merchants.

User device 110, wearable device 102, merchant server 140, and paymentprovider server 170 may each include one or more processors, memories,and other appropriate components for executing instructions such asprogram code and/or data stored on one or more computer readable mediumsto implement the various applications, data, and steps described herein.For example, such instructions may be stored in one or more computerreadable media such as memories or data storage devices internal and/orexternal to various components of system 100, and/or accessible overnetwork 160.

Network 160 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 160 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks.

User device 110 may be implemented using any appropriate hardware andsoftware configured for wired and/or wireless communication over network160. For example, in one embodiment, user device 110 may be implementedas a personal computer (PC), a smart phone, wearable computing device,laptop computer, and/or other types of computing devices capable oftransmitting and/or receiving data, such as an iPad™ from Apple™.

User device 110 may include one or more browser applications 115 whichmay be used, for example, to provide a convenient interface to permituser 105 to browse information available over network 160. For example,in one embodiment, browser application 115 may be implemented as a webbrowser configured to view information available over the Internet, suchas a user account for setting up a shopping list and/or merchant sitesfor viewing and purchasing products and services. User device 110 mayalso include one or more toolbar applications 120 which may be used, forexample, to provide client-side processing for performing desired tasksin response to operations selected by user 105. In one embodiment,toolbar application 120 may display a user interface in connection withbrowser application 115.

User device 110 may further include other applications 125 as may bedesired in particular embodiments to provide desired features to userdevice 110. For example, other applications 125 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 160, or othertypes of applications.

Applications 125 may also include email, texting, voice and IMapplications that allow user 105 to send and receive emails, calls, andtexts through network 160, as well as applications that enable the userto communicate, transfer information, make payments, and otherwiseutilize a digital wallet or account through the payment provider asdiscussed herein. User device 110 includes one or more user identifiers130 which may be implemented, for example, as operating system registryentries, cookies associated with browser application 115, identifiersassociated with hardware of user device 110, or other appropriateidentifiers, such as used for payment/user/device authentication. In oneembodiment, user identifier 130 may be used by a payment serviceprovider to associate user 105 with a particular account maintained bythe payment provider. A communications application 122, with associatedinterfaces, enables user device 110 to communicate within system 100.

Wearable device 102 may be connected to (e.g., in electroniccommunication with) user device 110. Wearable device 102 may be adisplay device, such as a smart watch. Wearable device 102 may include adisplay 104. Wearable device 102 may be connected to user device 110 bywire or wirelessly. For example, wearable device 102 may be connected touser device 110 via Bluetooth or other NFC. Bluetooth or NFC signals maybe communicated between user device 110 and wearable device 102. Forexample, wearable device 102 may be paired wirelessly with user device110 to establish wireless communication. Display information signalsand/or control signals may be communicated wirelessly between wearabledevice 102 and user device 110. Control or display information signalsmay be communicated between the wearable device 102 and user device 110via Bluetooth or other NFC.

Wearable device 102 may include a touch screen display 104. Display 104may display information sent from user device 110. User operations andinputs on display 104 may be sent from wearable device 102 to userdevice 110. For example, user 105 may press or swipe on display 104 tonavigate among different pages of information or functions displayed ondisplay 104. In an embodiment, physical buttons may be provided onwearable device 102 to receive user 105's input to operate wearabledevice 102. Wearable device 102 may be waterproof, such that user 105may operate wearable device 102 under water. Thus, user 105 may usewearable device 102 to indirectly implement various functions of userdevice 110, such as making/receiving payments, when user 105 is wearingwearable device 102 under water or in other conditions not suitable foruser device 110.

Wearable device 102 may include various sensors, such as microphones,temperature sensors, accelerometers, finger scanners, and the like. Thevarious sensors may collect various biometric information of the user,such as heart rate, voice pattern, speech pattern, finger print, touchpattern, and the like. The various biometric information may be used toidentify or authenticate the user. For example, the various biometricinformation may be collected and catalogued at the payment providerserver 170 and may be used to authenticate user at another device or atother contexts, such as for comparison with current captured biometricinformation.

Wearable device 102 also may include a camera or scanner configured toscan or capture images. For example, the wearable device 102 may scan abar code or a Quick Response (QR) code of a product from which theproduct may be identified and price comparison may be performed.Wearable device 102 also may include a microphone configured to capturethe user's voice commands. The voice commands may be used to implementand control the payment application installed at user device 110. Forexample, various payment related actions, such as “order,” “send money,”“request money,” “check in to merchant,” “find a coupon for coffee,”“send $5 to XX,” may be initiated by voice command captured at thewearable device 102.

Merchant server 140 may be maintained, for example, by a merchant orseller offering various products and/or services. The merchant may havea physical point-of-sale (POS) store front. The merchant may be aparticipating merchant who has a merchant account with the paymentservice provider. Merchant server 140 may be used for POS or onlinepurchases and transactions. Generally, merchant server 140 may bemaintained by anyone or any entity that receives money, which includescharities as well as banks and retailers. For example, a payment may bea donation to a charity or a deposit to a saving account. Merchantserver 140 may include a database 145 identifying available products(including digital goods) and/or services (e.g., collectively referredto as items) which may be made available for viewing and purchase byuser 105. Accordingly, merchant server 140 also may include amarketplace application 150 which may be configured to serve informationover network 160 to browser 115 of user device 110. In one embodiment,user 105 may interact with marketplace application 150 through browserapplications over network 160 in order to view various products, fooditems, or services identified in database 145.

Merchant server 140 also may include a checkout application 155 whichmay be configured to facilitate the purchase by user 105 of goods orservices online or at a physical POS or store front. Checkoutapplication 155 may be configured to accept payment information from oron behalf of user 105 through payment service provider server 170 overnetwork 160. For example, checkout application 155 may receive andprocess a payment confirmation from payment service provider server 170,as well as transmit transaction information to the payment provider andreceive information from the payment provider (e.g., a transaction ID).Checkout application 155 may be configured to receive payment via aplurality of payment methods including cash, credit cards, debit cards,checks, money orders, and the like.

Payment provider server 170 may be maintained, for example, by an onlinepayment service provider which may provide payment between user 105 andthe operator of merchant server 140. In this regard, payment providerserver 170 includes one or more payment applications 175 which may beconfigured to interact with user device 110 and/or merchant server 140over network 160 to facilitate the purchase of goods or services,communicate/display information, and send payments by user 105 of userdevice 110.

Payment provider server 170 also maintains a plurality of user accounts180, each of which may include account information 185 associated withconsumers, merchants, and funding sources, such as banks or credit cardcompanies. For example, account information 185 may include privatefinancial information of users of devices such as account numbers,passwords, device identifiers, user names, phone numbers, credit cardinformation, bank information, or other financial information which maybe used to facilitate online transactions by user 105. Advantageously,payment application 175 may be configured to interact with merchantserver 140 on behalf of user 105 during a transaction with checkoutapplication 155 to track and manage purchases made by users and whichand when funding sources are used.

A transaction processing application 190, which may be part of paymentapplication 175 or separate, may be configured to receive informationfrom user device 110 and/or merchant server 140 for processing andstorage in a payment database 195. Transaction processing application190 may include one or more applications to process information fromuser 105 for processing an order and payment using various selectedfunding instruments, including for initial purchase and payment afterpurchase as described herein. As such, transaction processingapplication 190 may store details of an order from individual users,including funding source used, credit options available, etc. Paymentapplication 175 may be further configured to determine the existence ofand to manage accounts for user 105, as well as create new accounts ifnecessary.

FIG. 2 is a flowchart showing a process 200 for facilitating paymentsusing a wearable device 102 according to one embodiment. At step 202,user device 110 may detect a connection of wearable device 102. Userdevice 110 may connect wirelessly to wearable device 102 via Bluetoothor NFC. For example, user device 110 may detect a wireless request fromwearable device 102 to register or setup a wireless connection withwearable device 102. For Bluetooth peripheral devices, user device 110may perform a wireless pairing process with the Bluetooth peripheraldevices to establish wireless Bluetooth connections. In one embodiment,user device 110 may connect to multiple wireless peripheral devicessimultaneously. For example, user device 110 may connect to a Bluetoothearpiece and a stereo system of a car simultaneously.

At step 212, user device 110 may generate and send display informationto wearable device 102 to be displayed on wearable device 102. In anembodiment, the display information may be generated by the paymentservice provider at payment provider server 170 and forwarded towearable device 102 via user device 110. The display information mayinclude notifications, offers from various merchants, transactioninformation, controls to be operated by user 105, and the like. Forexample, the display information may include payment notificationsindicating that user 105 has been paid, transaction history showing user105's previous transactions received or sent, offers from merchants,payment account information, and the like.

At step 214, user device 110 or payment provider server 170 may receiveuser's operations and input at wearable device 102. For example, buttons(physical or virtual) may be displayed on a touch screen of display 104to be operated by user 105. User 105 may confirm payments, send/receivepayments, navigate among different pages of display, and the like, suchas by operating various buttons. In an embodiment, physical buttons maybe provided on wearable device 102 to receive instructions and inputfrom user 105.

At step 216, user device 110 or payment provider server 170 may processtransactions or other functions based on user's input at wearable device102. For example, user 105 may operate wearable device 102 tomake/receive payments, view transactions, offers, nearby merchants,check-in to stores, and the like.

FIG. 3 is a diagram illustrating interactions between a wearable device102 and a user device 110 according to an embodiment. The user device110 may be a mobile cellular phone, a tablet computer, a laptopcomputer, or any computing device capable of communicating via wirelesscommunication, such as Bluetooth communication, Near Field Communication(NFC), or low energy Bluetooth communication (BLE). In particular, apayment application, such as a PayPal wearable application may beinstalled in user device 110 to manage and facilitate communication withvarious wearable devices. The payment application may includecommunication modules for various platforms or formats, such as platformspecific bridges, for communicating with wearable devices with variousoperating systems. The various wearable devices may include smartwatches, smart glasses, user interface in automobiles, or any devicescapable of receiving and displaying information.

The wearable device 102 may be connected to the user device 110wirelessly. User device 110 may determine the platform or formatcompatible to the wearable device 102 and may generate and formatinformation accordingly to be displayed at the wearable device 102. Inan embodiment, the wearable device 102 may be tethered or linked to theuser device 110 automatically when the wearable device 102 is in theproximity of the user device 110 or is in the wireless broadcast rangeof user device 110. In one embodiment, the range is small, e.g., lessthan two feet, such that the likelihood of wearable device 102 pairingwith a communication device of another user is greatly reduced. Thisrange can be set to a maximum range the user expects between thewearable device and the user device. The communication between the userdevice 110 and the wearable device 102 may be encrypted for additionalsecurity.

For example, as shown in FIG. 5, a PayPal wearable app may be installedinto a mobile cellular phone. The PayPal wearable app may ask the userto link the user device 110 with the wearable device 102 by entering aPIN or password at the user device 110 to authenticate the user 105.Other methods of user authentication, such as by voice recognition,facial recognition, fingerprint scanning, and the like, also may be usedto authenticate the user. An option may be provided to allow thewearable device 102 to be continuously linked or logged in with thepayment application at the user device 110. The wearable device 102 maydisplay payment related information from the payment applicationinstalled at the user device 110 when the wearable device 102 is linkedto the user device 110.

After the wearable device 102 is linked with or logged into the paymentapplication at the user device 110, the user may implement variouspayment related functions via the wearable device 102. For example,information received at the user device 110, such as merchant offers,store check-in notifications, payment codes, or other purchase orpayment related to information, may be displayed at the wearable device102. Further, the user's payment account information, such as accountbalance, transaction history, transaction alerts, and the like, may bedisplayed at the wearable device 102.

In some embodiments, the wearable device 102 may be a standalone deviceoperating without the user device 110. As such, the user 105 may operatethe wearable device 102 to implement various transactions without theuser device 110. For example, the wearable device 102 may incorporatecomponents and functions of the user device 110. Thus, the user 105 maymake transactions using the wearable device 102, without the user device110.

FIG. 6 illustrates exemplary screen shots of user device 110 for settingup wearable device 102 with user device 110. In particular, user 105 mayinput different settings for how wearable device 102 interacts with userdevice 110. For example, user 105 may link user 105's payment account touser device 110 and/or wearable device 102. User 105 also may set up howand when the wearable device 102 is linked to user device 110. Inaddition, user 105 may set up how and when the wearable device 102synchronizes with user device 110.

As shown in screen 610, interface may be provided for user 105 to inputselections for various settings. For example, user 105 may choose tosend payment notifications using wearable device 102. Selections forallowing balance and transactions to be shown on wearable device 102also may be provided. An option may be provided to allow sending andrequesting money or payments using wearable device 102. Another optionmay be provided to allow check-in and payment at nearby stores. Ifpayment at nearby store is selected, user 105 may be requested to add apicture and/or link a funding source, such as credit card or bankaccounts, for payments. Another option may be provided to choose howuser 105 may check-in at favorite stores, such as automatically ormanually.

As shown in screen 620, an interface is provided to allow user 105 tologin to user 105's payment account for payment or other transactions.User 105 is requested to enter a PIN or password and a virtual keypad isdisplayed to receive user 105's input. User 105 also is allowed tochoose to be logged in until user 105 log out. Thus, user interface,such as screen 610 and screen 620, may be provided at user device 110 toallow user 105 to set up how wearable device 102 may be used forfacilitating payments and other payment related functions.

FIG. 7 is a user interface navigation flow chart for a wearable deviceaccording to one embodiment. The information for displaying differentscreens may be generated at user device 110 or payment provider server170 and sent to wearable device 102 to be displayed on the displayscreen 104. Screen 700 may be the home screen displaying a logo of thepayment service provider. The home screen may indicate to user 105 thatwearable device 102 is now executing a payment application. For example,wearable device 102 may be a smart watch that typically displays timeand date. User 105 may perform a gesture on the touch screen of wearabledevice 102, such as tracing the letter “P” or double tapping, to invokethe payment application on the wearable device 102. User 105's input maybe forwarded to user device 110 and/or payment provider server 170which, in response, may begin to send display information for thepayment application to wearable device 102.

From the home screen 700, user 105 may swipe left or right to go to adifferent function screen. For example, from the home screen 700, user105 may swipe right to see the store list screen 701. Store list screen701 may display a list of nearby stores or merchants and their relativedistance from user device 110. User device 110 may determine locationand position via GPS or other positioning techniques and may search fornearby merchants and stores. The list of merchants and stores may bedisplayed on wearable device 102. As shown in screen 701, Café 10 Star .. . is 10 feet away.

User 105 may tap on one of the stores or merchants to view more detailsof the merchant. For example, if user 105 taps on Café 10 Star on screen701, screen 702 may be displayed to show the name of the merchant “Café10 Starbucks,” the distance of the merchant from user 105 (10 feet), andoffers or promotions at the merchant (1 offer). A slider bar also may beprovided for user 105 to operate to make payment at this merchant. Ifuser 105 selects a check-in function, a screen 703 may be displayed toindicate that user 105 is located at and checked-in with a merchant. Ifthe merchant is a favorite of user 105, special effects or visualimages/graphics, such as a star, may be used to indicate as such. Afteruser 105 is checked into a merchant or a store, user 105 mayautomatically be signed into user 105's payment account ready to makepayments at the checked in location.

From the home screen 700, if user 105 swipes left, a balance and summaryscreen 704 may be displayed at wearable device 102. The balance andsummary screen 504 may display a balance summary of user 105's paymentaccount for a current period. The balance summary may include thecurrent balance ($121.50) and recent transactions, such as payment sent(one transaction of $3.50), payment received (two transactions totaled$125.00), and values of various offers (on offer valued at $5.00). User105 may swipe up to review details of the transactions on screens 505and 506. Details of transactions may include sender and/or receiver oftransaction, amount of transaction, time and date of transactions, fees,and service provider of the transactions.

From the balance and summary screen 704, user 105 may swipe left to showthe payment function screen 707 for sending payments or swipe left againto show the payment function screen 708 for receiving payments orrequesting money. Referring to FIG. 10, if user 105 selects to sendmoney on screen 707, wearable device 102 may display screen 1001including a virtual key pad for user 105 to enter the amount of money tobe sent. After user 105 enters the amount, screen 1002 may be displayedto allow user 105 to enter the recipient of the payment. The recipientmay be selected from user 105's list of contacts on user device 110.

After user 105 enters the recipient, screen 1003 may be displayed toallow user to select the funding source of the payment, such as a bankaccount, a credit card, or the payment account. After user 105 selects afunding source, screen 1004 may be displayed to allow user to enter amessage to be sent along with the payment. User 105 may skip or enter amessage. After screen 1004, screen 1005 may be displayed to show asummary of the payment transaction and for user 105 to confirm and sendthe payment. User 105 may confirm and send or cancel the paymenttransaction on screen 705. If user 105 confirms and sends the payment,screen 1007 may be displayed to indicate the sending process and thecompletion of the sending process.

FIG. 8 illustrates various screens for various functions displayed on awearable device according to one embodiment. As shown on Screens 801 and802, a number may be displayed along an upper right corner of the logoof the payment service provider to indicate the number of new or unreadnotifications for user 105. Screen 803 displays an account summary ofuser 105's payment account including recent transactions. Password orPIN may be required on screen 804 to view other information. Screen 805displays a notification that user 105 has received $125 from a friend.Screen 806 notifies user 105 of nearby offers including a number ofoffers displayed at an upper right corner of the screen. Screen 807notifies that user 105 is checked in at a Starbucks store. Further,wearable device 102 may vibrate to indicate that user 105 isautomatically checked in and payment may be made. If payment is made,screen 808 may be displayed to indicate that a payment is made viawearable device 102.

FIG. 9 illustrates various notifications displayed on a wearable deviceaccording to one embodiment. Screen 901 may be displayed when the useris checked in at a location or a merchant. For example, when the userenters a Starbucks coffee shop, user device 110 may detect the user'slocation and may check in at the coffee shop. A notification may begenerated and displayed on the wearable device 102, as shown on screen901. Further, the wearable device 102 may vibrate to alert the user ofthe check in. This may indicate to the user that the user may makepayments at the coffee shop via the wearable device 102.

Screen 902 may be displayed when a payment transaction is made. Forexample, after purchasing a cup of coffee, the user may pay for thecoffee using the wearable device 102. After the payment transaction, anotification may be displayed to indicate that $3.50 has been paid toStarbucks, as shown on screen 702.

Screen 903 may be displayed when a payment has been received by theuser. For example, if the user receives money from a friend, thenotification may be displayed on the wearable device 102 to indicatethat $125 is received from David M. Further, the friend may include amessage with the payment to describe the payment, such as “thanks fordinner” indicating that the payment is for their dinner together.

Screen 904 may be displayed when the link between the wearable device102 and the payment application at user device 110 is about to bedisconnected. In particular, the link between wearable device 102 anduser device 110 may be maintained for a particular period of time, suchas 8 hours. The user is requested to confirm the link every 8 hours tomaintain the link. As such, when the 8 hour period is about to expire,screen 704 may be displayed to notify the user and ask the user to tapto stay logged in at the payment application of user device 110. If theuser taps the screen, the link between wearable device 102 and thepayment application at user device 110 may be maintained for another 8hours or other time period. If the user does not tap the screen and thetime period expires, screen 905 may be displayed to indicate that theuser is required to re-establish the link between wearable device 102and the payment application at user device 110 by logging in at userdevice 110.

FIG. 11 illustrates a user interface navigation flow chart showingvarious functions displayed on a wearable device according to oneembodiment. Home screen 1101 may display a logo of the payment serviceprovider. If user 105 swipes left, an account summary of user 105 at thepayment service provider may be displayed on screen 1102. If user 105swipes left once more, transaction activities may be displayed on screen1103. User 105 may scroll down/swipe up to view more transactionsdisplayed on screens 1106-1110 showing various payments at variousmerchants. For example, payments to merchants, such as Target, Walmart,Café 17, and Starbucks, are shown in negative amounts. Paymentsreceived, such as payment received from Richard Marc, are shown inpositive amounts.

From screen 1103, if user 105 swipes left, offers from nearby merchantsmay be displayed at screen 1104. User 105 may scroll down/swipe up toview more offers from various merchants displayed on screen 1111-1116.Each offer is displayed with a save button to allow the user 105 to savean offer for later use. The saved offers may be applied to purchasesmade by user 105. From screen 1104, if user 105 swipes left, nearbymerchants may be displayed on screen 1105. User 105 may scrolldown/swipe up to view more merchants located nearby displayed on screens1117-1122. User 105 may select one or more merchant to make purchases.For example, if the user press a save button on screen 1115 to save theoffer “$1 off,” a notification may be displayed on screen 1116indicating that the offer has been saved and will be applied for thenext purchase.

A pay button may be provided to make payment to a merchant. If a paymenthas been made, a notification may be displayed indicating that a certainamount is paid to that merchant. For example, if the use press the paybutton in screen 1121 to pay Luma, Ltd. After the payment truncation iscompleted, a notification is displayed on screen 1122 indicating thatthe payment has been made. An order button may be provided to orderproducts or services from a merchant. If user presses the order button,an application at user device 110 may be activated to receiveproduct/service selections and orders from user 105.

FIG. 12 illustrates various screens for various functions displayed on awearable device according to one embodiment. For example, screen 1201may display a balance amount of the user's payment account. The user mayswipe left and right on a screen of the wearable device 102 to navigatebetween different functions or features. The user may navigate amongscreens 1201-1204 by swiping left or right. Screen 1202 displays a listof transactions recently made via the payment account of the user. Theuser may swipe up or down to scroll through the list of transactions.Further, the user may tap on one of the transactions to view details ofthe tapped transaction. For example, if the user taps the transactionfor Jamba Juice in screen 1202, the wearable device 102 may displayscreen 1205 including details of the transaction at Jamba Juice. Theuser also may swipe right of left on screen 1205 to go to the nextdetail transaction on the list.

Screen 1203 displays a list of offers from nearby merchants. The usermay swipe up or down to scroll through the list of offers. The user maytap on one of the offers for a detail view of the tapped offer. Forexample, if the user taps the $2 off offer at Farmer's Market on screen1203, screen 1206 may be displayed to show details of the offer fromFarmer's Market. In particular, a button may be provided at screen 1206to allow the user to save or accept the offer. As such, the offer may beapplied toward the user's current or future purchase at the Farmer'sMarket.

Screen 1204 displays a list of shops or merchants near the user. Theuser may swipe up or down to scroll through the list of shops ormerchants. The user may tap one of the shops of merchants to implementpayment transactions at the tapped store or merchant. For example, ifthe user taps Farmer's Market at screen 1204, screen 1207 may bedisplayed to allow the user to make payments at Farmer's Market. Inparticular, screen 1207 may indicate that a $2 off coupon previouslysaved by the user is automatically applied to the purchase. If the usertaps the pay button on screen 1207, a QR code or a bar code may bedisplayed to be scanned by the merchant to process or confirm payment.After the payment transaction, a screen may be displayed to confirm thatthe payment transaction has been processed successfully.

Accordingly, various information related to shopping, payments, offers,and the like, may be communicated from the user device 110 to thewearable device 102 to be displayed to the user 105. A navigationinterface may be provided to allow the user 105 to navigate variousinformation at the wearable device 102. Various user instructions alsomay be received at the wearable device 102 and communicated to the userdevice 110 for making transactions.

FIG. 4 is a block diagram of a computer system 400 suitable forimplementing one or more embodiments of the present disclosure. Invarious implementations, the user device may comprise a personalcomputing device (e.g., smart phone, a computing tablet, a personalcomputer, laptop, wearable computing device, Bluetooth device, key FOB,badge, etc.) capable of communicating with the network. The merchantand/or payment provider may utilize a network computing device (e.g., anetwork server) capable of communicating with the network. It should beappreciated that each of the devices utilized by users, merchants, andpayment providers may be implemented as computer system 400 in a manneras follows.

Computer system 400 includes a bus 402 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 400. Components include aninput/output (I/O) component 404 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons orlinks, etc., and sends a corresponding signal to bus 402. I/O component404 may also include an output component, such as a display 411 and acursor control 413 (such as a keyboard, keypad, mouse, etc.). Anoptional audio input/output component 405 may also be included to allowa user to use voice for inputting information by converting audiosignals. Audio I/O component 405 may allow the user to hear audio. Atransceiver or network interface 406 transmits and receives signalsbetween computer system 400 and other devices, such as another userdevice, a merchant server, or a payment provider server via network 160.In one embodiment, the transmission is wireless, although othertransmission mediums and methods may also be suitable. A processor 412,which can be a micro-controller, digital signal processor (DSP), orother processing component, processes these various signals, such as fordisplay on computer system 400 or transmission to other devices via acommunication link 418. Processor 412 may also control transmission ofinformation, such as cookies or IP addresses, to other devices.

Components of computer system 400 also include a system memory component414 (e.g., RAM), a static storage component 416 (e.g., ROM), and/or adisk drive 417. Computer system 400 performs specific operations byprocessor 412 and other components by executing one or more sequences ofinstructions contained in system memory component 414. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 412 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious implementations, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 414, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 402. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 400. In various other embodiments of thepresent disclosure, a plurality of computer systems 400 coupled bycommunication link 418 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A system comprising: a non-transitory memory; andone or more hardware processors coupled to the non-transitory memory andconfigured to read instructions from the non-transitory memory to causethe system to perform operations comprising: detecting, via a softwareapplication running on a computing device of a user, that a wearabledevice is communicatively coupled with the computing device via a shortrange wireless communication protocol, wherein the software applicationis associated with a payment service provider and is configured toenable the user to access a set of electronic transactionfunctionalities associated with a payment account with the paymentservice provider via the computing device based on one or moreauthentication credentials received from the computing device thatauthenticate the user; determining, for the wearable device, a subset ofaccount activities available for the payment account based on a risklevel for the subset of account activities, wherein the subset ofaccount activities comprise the set of electronic transactionfunctionalities, and wherein the subset of account activities enable avoice control for processing transactions using the set of electronictransaction functionalities; in response to the detecting, establishinga session that links the wearable device with the computing device toenable the wearable device to access the set of electronic transactionfunctionalities associated with the payment account based on the one ormore authentication credentials received from the computing devicewithout requiring any user input via the computing device, wherein thesession is associated with an expiration time upon which the wearabledevice is no longer linked with the computing device and the set ofelectronic transaction functionalities associated with the paymentaccount is no longer accessible by the wearable device; receiving, viathe voice control from a voice command to the wearable device, a requestdirectly from the wearable device for performing a first electronictransaction corresponding to one of the set of electronic transactionfunctionalities using the payment account; determining a confidencelevel that the user provided the voice command to the wearable device;in response to determining that the user provided the voice commandbased on the confidence level, determining that the request is receivedprior to the expiration time; in response to determining that therequest is received prior to the expiration time and without requiringany user input via the computing device, processing the first electronictransaction using the payment account based on the one or moreauthentication credentials received from the computing device; obtainingbiometric sensor data directly from the wearable device collected by oneor more sensors of the wearable device, wherein the obtained biometricsensor data is different from the one or more authenticationcredentials; determining that the obtained biometric sensor data matchespreviously observed biometric sensor data associated with the user; inresponse to determining that the obtained biometric sensor data matchesthe previously observed biometric sensor data, automatically extendingthe session that links the wearable device with the computing device toenable the wearable device to access the set of electronic transactionfunctionalities associated with the payment account beyond theexpiration time based on the one or more authentication credentialsreceived from the computing device; and in response to processing thefirst electronic transaction, transmitting a notification indicating theprocessing of the first electronic transaction to the wearable device.2. The system of claim 1, wherein the wearable device is communicativelycoupled with the computing device via Bluetooth low energycommunication.
 3. The system of claim 1, wherein the operations furthercomprise transmitting the notification to the computing device.
 4. Thesystem of claim 1, wherein the operations further comprise: generating anotification indicating that the session is expiring within apredetermined period of time; and pushing the notification to thewearable device.
 5. The system of claim 4, wherein the notificationcomprises a selectable option to extend the session beyond theexpiration time; and wherein the session is extended for an additionallength of time when the selectable option is selected by the user. 6.The system of claim 1, wherein the operations further comprise:detecting a signal wirelessly received by the wearable device from abeacon of a merchant location associated with the payment account of theuser; and in response to detecting the signal, (i) automaticallychecking-in the user to the merchant location and (ii) causing thewearable device to provide an alert indicating that the user is checkedin at the merchant location.
 7. The system of claim 1, wherein thebiometric sensor data comprises at least one of voice data or locationdata.
 8. A computer-implemented method comprising: detecting, by aserver machine via a software application running on a computing deviceof a user, that a first wearable device is communicatively coupled withthe computing device via a short range wireless communication protocol,wherein the software application is associated with a payment serviceprovider and is configured to enable the user to access a set of paymentfunctionalities associated with a payment account with the paymentservice provider via the computing device based on one or morecredentials received from the computing device; determining, for thefirst wearable device, a subset of account activities available for thepayment account based on a risk level for the subset of accountactivities, wherein the subset of account activities comprise the set ofpayment functionalities, and wherein the subset of account activitiesenable a voice control for processing transactions using the set ofpayment functionalities; in response to the detecting, establishing, bythe server machine, a session that links the first wearable device withthe computing device to enable the first wearable device to access theset of payment functionalities associated with the payment account basedon the one or more credentials received from the computing devicewithout requiring any user input via the computing device, wherein thesession is associated with an expiration time upon which the firstwearable device is no longer linked with the computing device and theset of payment functionalities associated with the payment account is nolonger accessible by the first wearable device; receiving, by the servermachine via the voice control from a voice command to the first wearabledevice, a request directly from the first wearable device for performinga payment transaction associated with a first one of the set of paymentfunctionalities using the payment account; determining a confidencelevel that the user provided the voice command to the first wearabledevice; in response to determining that the user provided the voicecommand based on the confidence level, determining, by the servermachine, that the request is received prior to the expiration time; inresponse to determining that the request is received prior to theexpiration time, processing, by the server machine, the paymenttransaction using the payment account based on the one or morecredentials received from the computing device; obtaining, by the servermachine, biometric sensor data directly from the first wearable devicecollected by one or more sensors of the first wearable device, whereinthe obtained biometric sensor data is different from the one or morecredentials; determining, by the server machine, that the obtainedbiometric sensor data matches previously observed biometric sensor dataassociated with the user; in response to determining that the obtainedbiometric sensor data matches the previously observed biometric sensordata and without requiring any user input via the computing device,automatically extending, by the server machine, the session that linksthe first wearable device with the computing device to enable the firstwearable device to access the set of payment functionalities associatedwith the payment account beyond the expiration time based on the one ormore credentials received from the computing device; and in response toprocessing the payment transaction, transmitting, by the server machine,a notification indicating the processing of the payment transaction tothe first wearable device.
 9. The computer-implemented method of claim8, further comprising generating the notification based on aspecification of the first wearable device.
 10. The computer-implementedmethod of claim 9, further comprising generating a second notificationindicating the processing of the payment transaction to be displayed ata second wearable device connected to the computing device wirelesslybased on a second specification associated with the second wearabledevice.
 11. The computer-implemented method of claim 8, furthercomprising: receiving a second voice command from the user via the firstwearable device during the extended session; and translating the secondvoice command into a second request for performing a second paymenttransaction corresponding to a second one of the set of paymentfunctionalities using the payment account of the user based on the oneor more credentials received from the computing device.
 12. Thecomputer-implemented method of claim 11, further comprising furtherextending the extended session in response to receiving the second voicecommand.
 13. The computer-implemented method of claim 8, furthercomprising: receiving a scanned code from the first wearable device;determining a product based on the scanned code; and providing, at thefirst wearable device, a price comparison for the determined product.14. The computer-implemented method of claim 8, further comprising:subsequent to extending the session, receiving biometric informationfrom the first wearable device; and in response to receiving thebiometric information, further extending, automatically by the servermachine, the extended session for an additional period of time, at leastin part, based on the biometric information.
 15. Thecomputer-implemented method of claim 14, wherein the biometricinformation comprises at least one of a heart rate, a voice pattern, aspeech pattern, a fingerprint, or a touch pattern.
 16. Thecomputer-implemented method of claim 8, wherein the request comprises acode scanned by the first wearable device.
 17. A non-transitorymachine-readable medium having stored thereon machine-readableinstructions executable to cause a machine to perform operationscomprising: detecting, via a software application running on a computingdevice of a user, that a wearable device is communicatively coupled withthe computing device via a short range wireless communication protocol,wherein the software application is associated with a payment serviceprovider and is configured to enable the user to access a set offunctionalities associated with a payment account with the paymentservice provider via the computing device based on one or moreauthentication credentials received from the computing device thatauthenticate the user; determining, for the wearable device, a subset ofaccount activities available for the payment account based on a risklevel for the subset of account activities, wherein the subset ofaccount activities comprise the set of payment functionalities, andwherein the subset of account activities enable a voice control forprocessing transactions using the set of payment functionalities; inresponse to the detecting, establishing a session that links thewearable device with the computing device to enable the wearable deviceto access the set of functionalities associated with the payment accountbased on the one or more authentication credentials of the user receivedfrom the computing device without requiring any user input via thecomputing device, and wherein the session is associated with anexpiration time upon which the set of functionalities associated withthe payment account is no longer accessible by the wearable device;receiving, via the voice control from a voice command to the wearabledevice, a request from the wearable device for performing an electronictransaction corresponding to a first one of the set of functionalitiesusing the payment account; determining a confidence level that the userprovided the voice command to the wearable device; in response todetermining that the user provided the voice command based on theconfidence level, determining that the request is received prior to theexpiration time; in response to determining that the request is receivedprior to the expiration time and without requiring any user input viathe computing device, processing the electronic transaction using thepayment account based on the one or more authentication credentialsreceived from the computing device; obtaining biometric sensor datadirectly from the wearable device collected by one or more sensors ofthe wearable device, wherein the obtained biometric sensor data isdifferent from the one or more authentication credentials; determiningthat the obtained biometric sensor data matches previously observedbiometric sensor data associated with the user during a pastauthenticated user session; in response to determining that the obtainedbiometric sensor data matches the previously observed biometric sensordata, automatically extending the session that links the wearable devicewith the computing device to enable the wearable device to access theset of functionalities associated with the payment account beyond theexpiration time based on the one or more authentication credentialsreceived from the computing device; and in response to processing theelectronic transaction, transmitting a notification indicating theprocessing of the electronic transaction to the wearable device.
 18. Thenon-transitory machine-readable medium of claim 17, wherein theelectronic transaction comprises a payment transaction.
 19. Thenon-transitory machine-readable medium of claim 17, wherein the requestis initiated based on the user navigating an electronic contentdisplayed in a browser application running on the wearable device. 20.The non-transitory machine-readable medium of claim 17, wherein theoperations further comprise providing, on a display of the wearabledevice, a user interface for accessing the set of functionalitiesassociated with the payment account.